Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(eslint): only run circular dependency check on CI #421

Merged
1 commit merged into from
Dec 17, 2020
Merged

Conversation

ghost
Copy link

@ghost ghost commented Dec 16, 2020

This runs our circular dependency checks only on CI, to not slow down editors, as the checks can be very cpu intensive.

See the GH docs for the CI env var I'm using: GH actions docs. Besides GH actions, CI is a pretty common env var for indicating that code is running on CI so it should even work with most other providers. See also here: https://github.com/watson/ci-info/blob/master/index.js#L52.

Follow up

Also, as a follow up and if this works out, we can move this and related rules to cli-style and make it a rule we check for all our codebases: https://jira.dhis2.org/browse/CLI-19

@ghost ghost requested review from varl and a team December 16, 2020 11:18
Copy link
Contributor

@HendrikThePendric HendrikThePendric left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we need to set the env variable somewhere, like in a GitHub workflow?

Sorry, I assumed that env var wasn't there because I didn't see any changes for it. But I see we have it already:

So, these changes look good to me, but I'll let @varl approve (or request changes).

@cypress
Copy link

cypress bot commented Dec 16, 2020



Test summary

495 0 0 0


Run details

Project ui
Status Passed
Commit 3b87c4b
Started Dec 16, 2020 11:20 AM
Ended Dec 16, 2020 11:25 AM
Duration 04:12 💡
OS Linux Ubuntu - 18.04
Browser Electron 80

View run in Cypress Dashboard ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

@ghost
Copy link
Author

ghost commented Dec 16, 2020

Don't we need to set the env variable somewhere, like in a GitHub workflow?

Sorry, I assumed that env var wasn't there because I didn't see any changes for it. But I see we have it already:

That shouldn't even be necessary, the GH actions docs have it listed as always set to true under their default env vars for runner environments.

@HendrikThePendric
Copy link
Contributor

That shouldn't even be necessary, the GH actions docs have it listed as always set to true under their default env vars for runner environments.

Thanks for pointing that out.

@ghost
Copy link
Author

ghost commented Dec 16, 2020

That shouldn't even be necessary, the GH actions docs have it listed as always set to true under their default env vars for runner environments.

Thanks for pointing that out.

N.p. 👍. That's how I interpret the docs at least. But maybe I'm missing sth. Or the defaults have changed. I'll wait for Viktor's feedback.

Copy link
Contributor

@varl varl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks alright to my eyes.

@ghost ghost merged commit 39fff3e into next Dec 17, 2020
@ghost ghost deleted the conditional-dep-check branch December 17, 2020 09:11
@dhis2-bot
Copy link
Contributor

@dhis2-bot
Copy link
Contributor

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants